…zing events as Cucumber Messages.

…ecutionEvents to one or more Message Sinks. Default implementation of one Sink that serializes Messages to an ndjson file per feature.

Not finished: hooking up the TestThreadExecution event handlers.

…mber Messages Publisher and Broker to the initialization sequence provided by the Plugin architecture.

…est project. The File Sink is hooked in as a nuget package.

Next: exploratory debugging to confirm the event listeners are wired up correctly at Feature start time.

Need to figure out why trace logging also not working.

…check of whether it had been initialized (temp).

(Temp) - added Debugger.Launch to FileSinkPlugin to force launch of debugger.

…Publisher from the FileSinkPlugIn completely.

…the use of a BlockingCollection. Eliminated base class for Sinks. Eliminated use of Async for MessageSinks. Sinks have to ensure their own thread-safety and non-blocking behavior. May want to revisit that.

…ke Messages (meta, Source, GherkinDocument, and Pickles).

… information into Messages. First example is transforming StepBinding classes into messages of type StepDefinition.

…Generator.

…pport for CucumberMessages for that feature.

…e, then all are published.

…ioState emit sequences of Envelopes for consumption by the Publisher.

…fter scenario completion so that we have full binding Match info available to create the TestCase message.

… simple scenarios.

minimal and pending scenarios added.

… which I don't think apply to the .NET implementation.

Need to add support for images and documents as embedded resources to be added to generated test projects before attachments and hooks can be implemented and tested.
Not yet added infrastructure to compare output ndjon with expected.

…lisher, Broker, and Sink). Returned FeatureTracker back to normal, sync methods.

…rectly serialized.

…at a FeatureFinishedEvent is received but not all Scenarios are yet marked as Finished, then the entire Feature success status should be set to False.

To match Main

…enarios in parallel

…when two Features were rewriting simultaneously.

…Enums, and TestHookStarted/Finished messages.

CCK compliance not yet available.

…hmentAdded events as Obsolete.

…ature class start-up. Modified FeatureInfo constructor to accept the FeatureMessages object as optional parameter. Had to modify a Runtime test to accomodate that change.

Also changed Generation such that we're more thoroughly emitting the 'global::' prefix on Reqnroll types (for Messages related types).
Marked the Non-Compliant CCK test scenarios as [Ignore].

…was failing now that is called well before the Messages configuration system is spun up.

…ce when throwing an 'already resolved' registration exception.

…Static Messages for a Feature were processed (which resulted in the PickleJar not being properly initialized).

Moving the FeatureTracker creation to within the double-check of the lock section (so that it is called only one time).

…thread safety.

From CCK

Updated FluentAssertion property selector rule to ignore the TestRunStartedId.

…s problems with RuntimeTests which fire events but without a full event orchestration as expected by the Publisher.

… the TraceListener until the moment its needed rather than as a constructor param. This avoids a conflict when the Test Frameworks provide their own implementation (which caused an 'oibject already resolved' error in the object container). Related changes in Tests to match.